====================================================================== IBIS INTERCONNECT MODELING AD HOC TASK GROUP MEETING MINUTES AND AGENDA http://www.eda.org/ibis/adhoc/interconnect/ Mailing list: ibis-interconn@freelists.org ====================================================================== Next Meeting Wednesday, May 13, 2009 8 AM US Pacific Time Telephone Bridge Passcode 916-356-2663 1 658-8675 (for international and alternate US numbers, contact Michael Mirmak) LiveMeeting: https://webjoin.intel.com/?passcode=6588675 Agenda: - Call for patents - Opens - Review of parser requirements document - Presentation on sparse matrices and port/node mapping (Walter Katz) ====================================================================== Minutes from May 6: Attendees: ---------- (* denotes present) Agilent - Radek Biernacki*, John Moore, Ken Wong Ansoft - Denis Soldo Cadence Design Systems - Terry Jernberg, Brad Griffin Cisco Systems - Mike LaBonte* Green Streak Programs - Lynne Green Hewlett-Packard - Rob Elliott Intel - Michael Mirmak* Mentor Graphics Corp. - John Angulo*, Vladimir Dmitriev-Zdorov Micron Technology - Randy Wolff Sigrity - Sam Chitwood, Raymond Y. Chen, Tao Su, Brad Brim SiSoft - Walter Katz* Teraspeed Consulting Group - Bob Ross* ======================================================================== No patents were declared. During opens, Michael described the requirements for and roles of parser bid committee members. John volunteered as bid committee member. Michael presented a proposed draft parser requirements document for comments. Bob commented that reasonable definitions were given for warning vs. error. In response to suggestions regarding corrections of file contents, Radek stated that he was not sure we should interfere with values of the data in the submitted files. Mike agreed that the phrasing of "impossible to use or interpret" as an error was not optimum. A cleaner way to specify errors is if the rule can specifically be found in the specification document and the submitted file violates it. He added that the proposal could include sensible numeric and consistency checks, as some checks are errors in the IBIS parser. These need not be included yet. Walter stated that individual values are used in several sections in Touchstone. For actual network data, the parser might verify that each value is a legal floating point number (no "ABC"). Frequencies should be monotonically increasing, for example, per the specification; never negative. Bob noted that warnings are usually used for data. He agreed with Mike on general error rules. There is no requirement that every warning/error have a line number. For example, a missing keyword will not have a line number. Hierarchically, pointing to the "next higher level" might be possible, but this structure doesn't really exist in Touchstone, as opposed to IBIS. Michael noted that the phrase "in memory" should be removed, as this may constrain the parser's speed and capabilities. Walter suggested putting "Linux" in as a separate OS to be supported. In addition, he proposed putting in a comment regarding minimizing differences between Oses. Michael asked about version control requirements. Mike responded that a "comma v" file containing source files and changes could be distributed with the source code. Bob stated that this may be overly constraining and vulnerable to updates, which may burden future developers. Version control can be deferred until a 2.1, etc. Michael asked the team what was missing in the document. Bob suggested the eventual developer will propose an as-yet unknown number of tests. The rough scope is about 50 error messages, assuming the parser must test each feature/keyword. Mike asked whether the code files should arrive with a copyright. Bob responded that this could be handled before final distribution. Bob noted that "tschk2" could be used as name but that this issue can be settled later ------------------------------------------------------------------ The IBIS Ad Hoc Interconnect Task Group Mailing List Archives are available at: http://www.freelists.org/archives/ibis-interconn TO UNSUBSCRIBE: Send a message to "ibis-interconn-request@freelists.org" with a subject of "unsubscribe" To administer your subscription status from the web, visit: http://www.freelists.org/list/ibis-interconn